Conversation
Co-authored-by: Destiny Hochhalter <117859673+des12437@users.noreply.github.com>
…reasViewTutorial.tutorial Co-authored-by: Ting <tchen@esri.com>
No force unwrapping needed
Between 200.7.0-4889 and 4990 this resource became unavailable in swift-toolkit-daily
feat(localization): update translation
Update translations for 200.7
Offline: Tutorial
`FeatureFormView` - Fix testCase_11_1 for visionOS
…eader.swift Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
…wift Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
…wift Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
…wift Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
…wift Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
…del.swift Co-authored-by: Caleb Rasmussen <crasmussen@esri.com>
Add `NavigationLayer`
mhdostal
left a comment
There was a problem hiding this comment.
this looks good and is a nice way to override the detentions when a component needs to.
|
A reservation I have with this approach is that supporting the same behavior for sheets seems problematic. Sheets (surprisingly) don't animate nicely when nested views with the Should we forego this magic approach and instead have developers manage their detents by adding more cases to |
Will this alleviate the problems with sheets? |
It doesn't seem to. There's some discussion about this issue here, but I haven't yet been able to make the suggestions work correctly with our views. Regardless, it might be best overall to take the sheet/panel agnostic approach and just report what the user is doing via the new cases suggested above on |
Ok. Let's try and make it the default/predominant use case work with little or not extra code. |
1934874 to
d2b5cf8
Compare

In certain situations, a view presented in a floating panel needs the map view to be revealed for user interaction:
Typically, this would require the presented view to have a binding to the floating panel's detent; however, the view might not be presented in a floating panel. By providing this internal preference, Toolkit components can communicate a preferred detent to the Floating Panel without developers needing to write any code. Example usage.
UtilityNetworkTrace.floatingPanelDetent(_:)be deprecated?